Benefits Verification Process API - Implementation Template
Setup guide
Importing Templates into Anypoint Studio
- In Studio, click the Exchange X icon in the upper left of the taskbar.
- Log in with your Anypoint Platform credentials.
- Search for the template
- Click Open.
Running Templates in Anypoint Studio
After you import your template into Studio, follow these configuration steps to run it.
Common Configuration
mule.env
- sets the environment where the application is to be deployed. It should be configured inconfig-<mule.env>.yaml
file. For a studio deployment, the recommended mule.env value islocal
.mule.key
- sets the encryption password to be used for encrypting secure properties. Update as needed.api.baseurl
- sets the base url of the api. Replace/override as needed when deploying to any environment. It should be configured inconfig-<mule.env>.yaml
file. Default value ishttps://localhost:8082/api
, whenmule.env
islocal
.api.autodiscoveryID
should be configured inconfig-<mule.env>.yaml
file.
Please refer to the attached link on how to secure the configuration properties.
HTTPS Configuration
https.host
— sets the service host interface. It should be configured inconfig-<mule.env>.yaml
file. (Defaults to 0.0.0.0 for all interfaces).https.port
— sets the HTTPS service port number. It should be configured inconfig-<mule.env>.yaml
file. (Default 8082).- TLS Configuration - Keystore properties setup:
keystore.alias
- sets the alias to the keystore. It should be configured inconfig-<mule.env>.yaml
file.keystore.path
- sets the path to the key file. Key should be availabe in /src/main/resources/keystore. It should be configured inconfig-<mule.env>.yaml
file.keystore.keypass
— sets keystore keypass to support HTTPS operation. It should be encrypted and configured inconfig-secured-<mule.env>.yaml
file.keystore.password
— sets keystore password to support HTTPS operation. It should be encrypted and configured inconfig-secured-<mule.env>.yaml
file.
Please refer to the attached link on how to generate the Keystore.
Benefits Verification Application Configuration
The application requires a few things to be configured, mainly the multiple system API connections
information. Configure them in the properties file located in the config/properties
folder.
sfdc-administration.host
should be configured inconfig-<mule.env>.yaml
file. The Organization and Patient resources from Administration System API are leveraged to fetch and sync required data into Health Cloud.sfdc-financial.host
should be configured inconfig-<mule.env>.yaml
file. CoverageEligibilityResponse resource from Financial System API is used to sync benefits to Health Cloud.cerner.administrationHost
should be configured inconfig-<mule.env>.yaml
file. Patient resource from Cerner Administration is used to fetch patient details.cerner.financialHost
should be configured inconfig-<mule.env>.yaml
file. Coverage resource from Cerner Financial is used to fetch Coverage details using Patient ID(FHIRID) as parameter.availity.host
should be configured inconfig-<mule.env>.yaml
file. Coverage resource is used to fetch benefit details using payer and memberId as search parameters.
Running it
- Right-click the template project folder.
- Hover your mouse over 'Run as'.
- Click Mule Application (configure).
- Inside the dialog, select Environment and set the variable mule.env to the appropriate value (e.g., dev or local).
- Inside the dialog, select Environment and set the variable mule.key to the property encryption key that you used to encrypt your secure properties.
- Click Run.
Deployment instructions for CloudHub using provided scripts
Ensure the Maven profile CloudHub-DEV
has been properly configured in your settings.xml
file. Reference can be found by downloading the Accelerator Common Resources asset. Additional instructions are available in the Getting Started with MuleSoft Accelerators - Build Environment guide.
Update the config-<env>.yaml
properties appropriately and then use one of the following scripts to deploy the application to Cloud Hub:
- packageDeploy.sh or deployOnly.sh (Mac/Linux).
- packageDeploy.cmd or deployOnly.cmd (Windows).
Testing it
- Use Advanced Rest Client or Postman to send a request over HTTPS. The template includes a postman collection in the
src/test/resources
folder. Update the collection variable(s) after successful import.